@sushihangover Could you please take a look at the build failure?

@carlosmn @Therzok @bording What's your opinion about this approach?

I might be missing something, but I'm not sure what it is this is trying to do.

The CustomBuildTasks project isn't something that is built on every build, the output is just saved to the repo and used via the targets files.

What problem is this trying to solve?

If this is about removing the .dll from the lib folder, then I'd think we'd be better off taking the NativeBinaries approach, and pull it in via NuGet.

Oh, I think I just figured out what it is you're trying to fix! You're trying to build on mono 4, and the CustomBuildTasks project is still using 3.5, which means the checked in dll is probably blowing up since mono 4 removed the 2.0 assemblies.

In that case, I would think the only thing that needs to be done is update CustomBuildTasks to net4, and then check in the new dll. Everything else should just work without any other changes at that point.

Both of the build tasks brought in via the targets files already work fine cross platform when using mono 3.12, so there shouldn't be any need for all of the workarounds/skipping them going on in this commit once the CustomBuildTasks assembly is built with net4.